ENT-14320: Wrapped most of the remaining cf-remote/cfbs commands into CFEngine-cli - #209

Isn't the whole point with CFEngine CLI that it should not be used in scripts? I feel options like --non-interactive kind of works against that. Do we already have these options for other sub commands?

Not for most commands, only init and for build/deploy. I added them as niceties when testing a module, that way I could just do cfengine build --host HOST --non-interactive and wait for output rather than pressing enter every 5 seconds.

We could consider

parser = argparse.ArgumentParser(prog='frobble')
parser.add_argument('--foo', help=argparse.SUPPRESS)
parser.print_help()

for arguments that are only for our tests.

I meant testing as in using. They way it would work without is that you would build, prompt if you want to deploy, then prompt if you want to run. But when working on a module/policy-set you would probably want to just fast-forward this and read the output after the full pipeline.